docs: point Node.js SDK versions and migration note to @flagsmith/nodejs - #8490
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 6 remain after this review. 📝 WalkthroughWalkthroughThe documentation identifies Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: 🔵 Low · up to The documentation correctly directs users to the renamed Node.js package, but existing integrations may still need the precise import replacement to complete migration safely. This is a bounded documentation risk. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Advanced
Run ID: 43c8dd2b-fc1c-4193-8628-6a14c91469b0
📒 Files selected for processing (2)
docs/docs/integrating-with-flagsmith/sdks/server-side.mdxdocs/plugins/flagsmith-versions/index.js
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.
2 participants
Summary
The Node.js SDK moved to
@flagsmith/nodejsat 9.0.0, but the docs still resolved versions from the oldflagsmith-nodejspackage, soNodejsVersion()and every tsdocs link on the server-side page pointed at 8.1.2.@flagsmith/nodejsin theflagsmith-versionsplugin.flagsmith-nodejs.Context
flagsmith-nodejscurrently carries no npm deprecation notice (unlikeflagsmith→@flagsmith/flagsmith), and it still gets ~25x the weekly downloads of@flagsmith/nodejs. Every publishedflagsmith-nodejsversion sends an unusable user agent, so that install base is invisible in SDK usage analytics. This PR should land alongside an npm owner running: